DOWNLOAD MATRIX

Download & Install SILO

Choose the server or admin client first, then use the install path that matches your operating system, architecture, and deployment model.

CURRENT SERVER RELEASE RELEASE.2026-08-06T00-00-00Z 2026-08-06 · amd64 / arm64

DATA SERVICE

SILO Server

Server binaries, container images, Linux packages, source, and Ansible playbook.

LinuxDockerKubernetesAnsiblemacOSWindows

Choose install method

ADMIN CLI

MCLI Client

A compatible command-line client for buckets, objects, identity, cluster administration, and daily operations.

LinuxmacOSWindowsDockerSource

Choose install method

01 / DATA SERVICE

SILO Server

From local validation to a multi-node production cluster, choose the delivery path that matches your control boundary.

CURRENT VERSION 2026-08-06 Release notes & all artifacts ↗

CONTAINER / MULTI-ARCH

Run a persistent instance in minutes

linux/amd64linux/arm64DockerPodmanDistroless

Best for local evaluation, development, and deployments that already use containers as the delivery boundary. The standard image bundles mcli, curl, and a shell.

The distroless variant ships the silo binary only, with a built-in silo healthcheck and support for any --user.

shell

docker pull pgsty/silo:RELEASE.2026-08-06T00-00-00Z
docker run -d --name silo --restart unless-stopped \
  -p 9000:9000 -p 9001:9001 \
  -v /data/silo:/data \
  -e MINIO_ROOT_USER=silo-admin \
  -e MINIO_ROOT_PASSWORD=replace-with-a-strong-secret \
  pgsty/silo:RELEASE.2026-08-06T00-00-00Z server /data --console-address :9001

shell

docker pull pgsty/silo:RELEASE.2026-08-06T00-00-00Z-distroless
docker run -d --name silo --restart unless-stopped \
  -p 9000:9000 -p 9001:9001 \
  -v /data/silo:/data \
  -e MINIO_ROOT_USER=silo-admin \
  -e MINIO_ROOT_PASSWORD=replace-with-a-strong-secret \
  pgsty/silo:RELEASE.2026-08-06T00-00-00Z-distroless server /data --console-address :9001

docker-compose.yml

# start with: docker compose up -d
services:
  silo:
    image: pgsty/silo:RELEASE.2026-08-06T00-00-00Z
    container_name: silo
    restart: unless-stopped
    command: server /data --console-address ":9001"
    ports: ["9000:9000", "9001:9001"]
    environment:
      MINIO_ROOT_USER: silo-admin
      MINIO_ROOT_PASSWORD: replace-with-a-strong-secret
    volumes:
      - silo-data:/data
    healthcheck:
      test: ["CMD", "silo", "healthcheck", "ready"]
      interval: 30s
volumes:
  silo-data:

docker-compose.yml

# the image carries its own HEALTHCHECK; no healthcheck: block needed
services:
  silo:
    image: pgsty/silo:RELEASE.2026-08-06T00-00-00Z-distroless
    container_name: silo
    restart: unless-stopped
    command: server /data --console-address ":9001"
    ports: ["9000:9000", "9001:9001"]
    environment:
      MINIO_ROOT_USER: silo-admin
      MINIO_ROOT_PASSWORD: replace-with-a-strong-secret
    volumes:
      - silo-data:/data
volumes:
  silo-data:

Docker Hub Migration guide → Container guide →

Example credentials are for local testing only. Enable TLS, use unique strong credentials, and test recovery before production. In-place self-update is disabled in SILO; upgrade by replacing the pinned image tag.

KUBERNETES / OPERATOR

Run SILO with the Tenant Helm Chart

Operator v7.1.1Helm 3.8+PVCTLS

The current MinIO Operator Tenant Chart supports overriding the tenant image repository, tag, or digest. Download the official values.yaml, point tenant.image at pgsty/silo, then configure pools and PVCs for your failure domains.

values.yaml

tenant:
  image:
    repository: pgsty/silo
    tag: RELEASE.2026-08-06T00-00-00Z
    pullPolicy: IfNotPresent

Tenant deployment guide View Helm chart ↗

In production, pin a tested tag or digest and review pools, StorageClass, anti-affinity, TLS, and tenant credentials before installation. In-place self-update is disabled in SILO. The upstream Operator repository is archived; treat v7.1.1 as a frozen compatibility baseline.

STANDALONE ARCHIVES

Download native, installer-free binaries

LinuxmacOSWindowstar.gz

Useful for CI, offline delivery, and hosts where you manage the systemd unit yourself. Every archive comes from the same GitHub release.

Linux

GNU / musl environments

x86_64silo_20260806000000.0.0_linux_amd64.tar.gz ARM64silo_20260806000000.0.0_linux_arm64.tar.gz

macOS

Intel / Apple Silicon

Intelsilo_20260806000000.0.0_darwin_amd64.tar.gz Apple Siliconsilo_20260806000000.0.0_darwin_arm64.tar.gz

Windows

PowerShell / Windows Server

x86_64silo_20260806000000.0.0_windows_amd64.tar.gz ARM64silo_20260806000000.0.0_windows_arm64.tar.gz

Linux x86_64

curl -fLO https://github.com/pgsty/silo/releases/download/RELEASE.2026-08-06T00-00-00Z/silo_20260806000000.0.0_linux_amd64.tar.gz
tar -xzf silo_20260806000000.0.0_linux_amd64.tar.gz
sudo install -m 0755 silo /usr/local/bin/silo
silo --version

PIGSTY / INFRA AS CODE

Deliver an operable SILO cluster with Ansible

TLSsystemdHAProxyMonitoring

Pigsty's MINIO module uses minio.yml to install packages, configure directories and certificates, launch systemd services, register monitoring, and provision aliases, buckets, and users. It fits deployments that need declarative configuration, TLS, and multi-node multi-disk topology.

Read the Pigsty MINIO docs ↗

Prepare the control node

shell

curl -fsSL https://repo.pigsty.io/get | bash
cd ~/pigsty
./bootstrap
./configure -g

Define the MinIO inventory

pigsty.yml

minio:
  hosts:
    10.10.10.10: { minio_seq: 1 }
  vars:
    minio_cluster: minio

Run the install playbook

ansible

./minio.yml -l minio
mcli ls sss/

Topology & configurationSNSD · SNMD · MNMD Playbook referenceinstall · config · launch · provision Four-node example4 nodes × 4 disks

SOURCE BUILD

Build from the maintained branch

Go 1.26+AGPLv3make

Use this path for auditing, development, or custom build flags. The result is a native silo executable for the current platform.

git + make

git clone https://github.com/pgsty/silo.git
cd silo
make build
./silo --version

Browse source Contributing →

02 / ADMIN CLI

MCLI Client

File transfer and administration commands for SILO, MinIO, and general S3-compatible storage. Standalone artifacts use the mcli command name.

CURRENT VERSION 2026-08-06 Release notes & all artifacts ↗

STANDALONE MCLI

Download the cross-platform client directly

LinuxmacOSWindows

Linux

server & workstation

x86_64mcli_20260806000000.0.0_linux_amd64.tar.gz ARM64mcli_20260806000000.0.0_linux_arm64.tar.gz

macOS

Intel / Apple Silicon

Intelmcli_20260806000000.0.0_darwin_amd64.tar.gz Apple Siliconmcli_20260806000000.0.0_darwin_arm64.tar.gz

Windows

desktop / server

x86_64mcli_20260806000000.0.0_windows_amd64.tar.gz ARM64mcli_20260806000000.0.0_windows_arm64.tar.gz

CONNECT TO LOCAL SILO mcli alias set local http://127.0.0.1:9000 ACCESS_KEY SECRET_KEY

CONTAINER CLIENT

Run mcli without installing it on the host

linux/amd64linux/arm64mc entrypoint

The container retains the familiar mc entrypoint, while standalone archives and Linux packages use mcli.

Docker

docker run --rm pgsty/mc:RELEASE.2026-08-06T00-00-00Z --version
docker run --rm pgsty/mc:RELEASE.2026-08-06T00-00-00Z ls play

Docker Hub

SOURCE BUILD

Build the maintained client

Go 1.26+AGPLv3make

The source keeps the github.com/minio/mc module path and mc build output for compatibility; release archives and packages use mcli.

git + make

git clone https://github.com/pgsty/mc.git
cd mc
make build
./mc --version

Browse source

DEPLOYMENT TOPOLOGY

Flexible deployment topology

SILO can start on one machine, but production planning should be explicit about disks, nodes, redundancy, and recovery expectations.

SNSD01 × 01

Single node · single disk

Personal labs, local development, and disposable non-production validation. No data redundancy.

silo server /data DEV / TEST

SNMD01 × 04+

Single node · multiple disks

A resource-constrained compromise that can tolerate some disk failures, but not node failure.

silo server /data{1...4} CONSTRAINED

MNMD04+ × 04+

Multiple nodes · multiple disks

The standard production topology, with erasure-code redundancy across disk and node failure domains. Recommended with Pigsty Ansible.

https://minio-{1...4}.pigsty/data{1...4} PRODUCTION

SUPPORT SURFACE

Need a production deployment path?

Move from local validation to production with the full documentation, release notes, and community support for upgrade and recovery planning.

Download & Install SILO

SILO Server

MCLI Client

SILO Server

Run a persistent instance in minutes

Run SILO with the Tenant Helm Chart

Install with native system packages

Download native, installer-free binaries

Linux

macOS

Windows

Deliver an operable SILO cluster with Ansible

Prepare the control node

Define the MinIO inventory

Run the install playbook

Build from the maintained branch

MCLI Client

Install the package for your Linux distribution

Download the cross-platform client directly

Linux

macOS

Windows

Run mcli without installing it on the host

Build the maintained client

Flexible deployment topology

Single node · single disk

Single node · multiple disks

Multiple nodes · multiple disks

Need a production deployment path?

Read the docs

Report an issue

Pigsty Ansible